Repository navigation
Conversation
2 of 4 tasks
simeng-li
reviewed
Nov 17, 2026
- Stage email and phone verification code MFA slots in interaction storage, include staged factors in MFA resolution and trusted-device eligibility, persist records on submit, and deduplicate singletons on merge. - Validate enabled MFA factors and allow enrolling an existing primary email or phone in POST /api/experience/profile/mfa without rewriting profile.
wangsijie
force-pushed
the
wangsijie-stage-email-phone-mfa-records
branch
from
November 17, 2026 08:15
8d2c2d8 to
f2cc711
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part of LOG-14721, PR 2a of "MFA: Explicit email/SMS factor enrollment" (stacked on #10028).
emailVerificationCodeandphoneVerificationCodeinMfainteraction storage, include staged verification-code factors in interaction MFA resolution and trusted-device proof eligibility, persistEmailVerificationCode/PhoneVerificationCoderecords on submission, and deduplicate singleton factor records inmergeUserMfaVerifications.POST /api/experience/profile/mfa(addVerificationCodeByVerificationId) to validate that the factor is enabled in sign-in experience and allow enrolling the user's existing primary email (case-insensitive) or primary phone (normalized) from a verified code record without staging a duplicate profile update.Testing
Unit tests
Checklist
.changeset